System and Method to Protect Sensitive Information via Distributed Trust

ABSTRACT

Multiple, separately administrated computer systems storing slices of the cipher text of a Personally Identifiable Information (PII) data item that is represented by a token. The token is used as a substitute of the data item. The data item is encrypted using a public key. To recover the data item, a complete set of the slices is retrieved from the separate computer systems and decrypted using the private key corresponding to the public key. Instances and circumstances of the usages of the data item can be recorded under the token in a blockchain ledger in connection with the retrieval and/or decryption of the cipher text. A data item owner may use the data item and the public key to recreate the cipher text, retrieve the token stored with the cipher text in the separate computer systems, and then query the ledger for a usage history of the data item.

RELATED APPLICATIONS

The present application claims the benefit of the filing date of Prov.U.S. Pat. App. 62/569,660, filed Oct. 9, 2017 and entitled “System andMethod to Protect Sensitive Information via Distributed Trust”, theentire disclosure of which is hereby incorporated herein by reference.

The present application is related to U.S. patent application Ser. No.15/078,804, filed Mar. 23, 2016 and entitled “Systems and Methods toProtect Sensitive Information in Data Exchange and Aggregation”, andU.S. patent application Ser. No. 15/685,305, filed Aug. 24, 2017 andentitled “Systems and Methods to Control Data Access and Usage”, theentire disclosures of which applications are hereby incorporated hereinby reference.

FIELD OF THE TECHNOLOGY

At least some embodiments disclosed herein relate to data storage andretrieval in general and more particularly but not limited to protectionof identity information in data storage and retrieval.

BACKGROUND

Personally Identifiable Information (PII) is data that could potentiallyidentify a specific individual. Information that can be used todistinguish one person from another and can be used for de-anonymizinganonymous data may be considered PII. PII can be used on its own or withother information to identify, contact, or locate a single person, or toidentify an individual in context. From PII the identity of acorresponding person can be reasonably ascertainable.

Examples of PII include full name, home address, email address, nationalidentification number, passport number, driver's license number,telephone number, credit card numbers, digital identity, IP address,login name, screen name, nickname, date of birth, birthplace, geneticinformation, facial image, fingerprints, or handwriting.

There is a need to protect PII for privacy, anonymity, and/or compliancewith rules, laws and regulations.

U.S. Pat. No. 7,933,841 discloses a system to track member consumercredit card transactions without receiving personal information fornon-members by using a one way hash function. In such a system, aone-way hash function is applied to personal information (e.g., a creditcard number) to obtain fingerprints that represent the personalinformation. The personal information in transaction data of credit cardusers is replaced by the fingerprints, where some of the users aremembers and some of the users are non-members. A computer having thepersonal information of the members can used the personal information togenerate the corresponding fingerprints to identify the transactions ofthe members without access to the personal information of thenon-members. The one way hash function makes it nearly impossible toreverse the fingerprints to the corresponding personal information thatthe computer does not already have.

Storing PII includes various risks of data breach. For example, a rougeagent, such as a database administrator or a data analyst, may take thepersonal information offsite. A hacker or group of hackers may gainadministrative access to the database infrastructure and thus the PIIstored therein. A person or two may collude to break the law and causedata breach. Trojan horses, and other infiltrating attacks have beensuccessful in causing data breach in not only PII but also associatedattributes.

Customers generally want a level of control over their information.Governments want to ensure the identity information of theirconstituents are safe.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which like referencesindicate similar elements.

FIG. 1 shows a system to protect data items according to one embodiment.

FIG. 2 shows a method to store a data item according to one embodiment.

FIG. 3 shows a method to retrieve a data item according to oneembodiment.

FIG. 4 shows a method to obtain a history of uses of a data itemaccording to one embodiment.

FIG. 5 shows a data processing system that can be used to implement someof the components of the system according to one embodiment.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding. However, in certain instances, wellknown or conventional details are not described in order to avoidobscuring the description. References to one or an embodiment in thepresent disclosure are not necessarily references to the sameembodiment; and, such references mean at least one.

Storing personal information of users within an organization carries therisk of massive data breach and that risk is getting greater with everyday.

To reduce and/or eliminate the risk, techniques disclosed herein store apiece of personal information as an encrypted data item that is slicedinto multiple portions for storage on multiple, separately administratedcomputer systems of different organizations.

As a result, decrypting the encrypted data item requires the assembly ofthe sliced portions that are separately stored in the separate systems.Thus, the risk of a massive data leak is significantly reduced; andbreaching one or more of the computer systems is insufficient to yielduseful information. Therefore, the trust of data security is distributedto a set of computer systems that are separately secured, administrated,and maintained.

An asymmetrical encryption method can be used to generate the encrypteddata item using a public key of a pair of private and public keys, wherethe decryption of the encrypted data item requires the use of theprivate key. It is impractical to derive the private key from the publickey; and the public key cannot be used to decrypt the cipher textgenerated using the public key. Thus, access control of the private keyfurther improves data security.

To establish data connections with the protected data items stored inthe system, a token is used to uniquely represent a data item among thedata items stored in the system. The token is used in place of the dataitem in establishing the data connections. When the use of the data itemitself is required, the token can be used by an authorized system toretrieve the corresponding data item.

It may be desirable to record the use instances of a data item itselfrepresented by a token, such that the use instances may be audited. Whenthe data item is decrypted for an instance of data use, the instance canbe recorded for the token in a blockchain ledger, in a way similar tothe recordation of a transaction of cryptocurrency. Thus, the blockchainledger has the usage history of the token of the data item, which can beretrieved for inspection. For example, an owner of the data item may usethe public key to generate the cipher text of the data item to look upthe token that is associated with the cipher text and then look up theusage history recorded for the token in the blockchain ledger.

In addition to recording the use instances of a data item, the systemcan be further extended to record an intended use (e.g., proposed by adata analyst for the use of the data) and/or a permitted use (e.g.,authorized by the consumer or original data custodian for the user ofthe data). Thus, an approval system can automate data use approval bymatching an intended use against a permitted use formulated using anontology or standardized nomenclature for specific data tokens. Such ausage can be recorded in a blockchain or distributed ledger for laterauditing as described above.

FIG. 1 shows a system to protect data items according to one embodiment.

In FIG. 1, a data item (105) is encrypted using an asymmetricalencryption method that involves a pair of a public key (107) and aprivate key (108), which are generated together in a key generationprocess. The public key (107) can be applied to the data item (105) togenerate the encrypted data item (106) in the phase of encryption (131);and the private key (108) can be applied to the encrypted data item(106) to recover the data item (105) in the phase of decryption (133).

Since it is not practical to derive the private key (108) from thepublic key (107), it is not necessary to restrict access to the publickey (107). Thus, the public key (107) can be published to enable theencryption (131) at a variety of computing devices, such as a usercomputer, a centralized server that provides the service, a purportedrecipient of the data item (105), etc.

To prevent unauthorized access, the private key (108) is not publishedand resides in a computer system that is authorized to perform thedecryption (133).

In FIG. 1, the data item (105) and the encrypted data item (106) arerepresented by a unique token (104). The token (104) uniquely identifiesthe data item (105) and/or the encrypted data item (106) among dataitems stored in the system.

For example, the data item (105) may contain a piece of PII, such as agovernment issued identification number of a person, an address, apayment account identifier, etc.

The token (104) may be generated based at least in part on the data item(105) and/or the encrypted data item (106) in some implementations. Forexample, a cryptographic, one-way hash of the data item (105) and/or theencrypted data item (106) may be used in generating the token (104).

In other implementations, the token (104) is generated independent ofthe data item (106). For example, a random number may be used for thetoken (104).

In some instances, the uniqueness of the token (104) is verified priorto its use as an identifier of the encrypted data item (106). Forexample, the system may check that the token (104) has not been used torepresent an existing date item stored in the system.

In some instances, the data item may be processed in a cleansing andstandardization operation to reduce duplicates. Items having the samecontent may be assigned the same token. For example, the encrypted dataitem (106) may be used as a key to search for a token (104) that isalready stored in the system in association with the encrypted data item(106).

The token (104) may be used as a substitute of the data item (105) inapplications where the actual content of the data item (105) is notused. For example, a social networking account may be registered to aperson that is identified using the data item (105). Instead of storingthe data explicitly connecting the social networking account with thedata item (105) of the person, the social networking account is storedin association with the token (104). Thus, if the database of the socialnetworking site identifying the association between accounts and thetokens representing the identities of their users is stolen, theidentities of the account users are still protected.

In FIG. 1, the token (104) and the encrypted data item (106) form a datarecord that is divided into multiple slices (121, 123, . . . , 125),which are stored in a set of separately managed computer systems (111,113, . . . , 115).

For example, some of the computer systems (111, 113, . . . , 115) areoperated by government entities; some of the some of the computersystems (111, 113, . . . , 115) are operated by banks; some of the someof the computer systems (111, 113, . . . , 115) are operated bynon-profit organizations; some of the computer systems (111, 113, . . ., 115) are operated by technology companies; some of the computersystems (111, 113, . . . , 115) are operated by credit bureau; etc.

The computer systems (111, 113, . . . , 115) of different organizationsand entities are combined on a computer network (e.g., Internet (103))to form a virtual distributed trust database (101) that stores (135) theslices (121, 123, . . . , 125) of a data record.

Some of the participants of the computer systems (111, 113, . . . , 115)may have a need to secure PII to provide their services, while othersmay have an interest in protecting PII of computer users in general.Through their contributions in the trust database (101), their risk ofmassive PII data breach is significantly reduced, since each of theorganizations is in possession only a slice of data for the recovery ofthe data item (105). Thus, gaining administrative privilege throughhacking or rouge agents in one or more of the computer systems (111,113, . . . , 115) is insufficient to cause massive leak of usefulinformation, such as PII.

In FIG. 1, any subset of the computer systems (111, 113, . . . , 115)does not have the complete token (104) and does not have the completeencrypted data item (106). To obtain the complete token (104) and/or thecomplete encrypted data item (106), it is necessary to have access toall of the computer systems (111, 113, . . . , 115) that are separatelysecured, managed, maintained, and administrated.

In FIG. 1, when only a subset of the slices (121, 123, . . . , 125) isavailable, the data item (105) cannot be decrypted even with the privatekey (108).

To retrieve (137) the complete set of slices (121, 123, . . . , 125), acomputer system is required to have authorized access to the entire setof computer systems (111, 113, . . . , 115).

In some implementations, data redundancy is built into the generation ofthe slices such that when more than a threshold number of slices areretrieved from a subset of the computer systems (111, 113, . . . , 115),the complete copy of the data record containing the token (104) and theencrypted data item (106) can be recovered and assembled. Such a trustdatabase (101) has improved reliability, such as when some of thesystems (111, 113, . . . , 115) is temporarily unavailable for variousreasons. Increasing the threshold number increases the data security ofthe trust database (101).

In FIG. 1, a blockchain ledger (102) is used to record the usages of thedata item (105) represented by the token (104).

For example, when a data record containing the token (104) and theencrypted data item (106) is retrieved (137) from the trust database(101) for a particular use, the instance of the use is recorded in theblockchain ledger (102) for the token (104). The use record stored inthe blockchain ledger (102) may include the identification of the token(104), a recipient of the data record for the recorded instance of theuse, and/or a description of the use, etc.

In some instances, a predetermined method is used to divide the datarecord of the token (104) and the encrypted data item (106) into theslices (121, 123, . . . , 125). Thus, it is not necessary to record datafor the retrieval (137) of the slices (121, 123, . . . , 125) forreconstruction of the data record.

Alternatively, or in combination, the creation of the slices (121, 123,. . . , 125) for storage in the trust database (101) is also recorded inthe blockchain ledger (102) to facilitate the retrieval (137) of theslices (121, 123, . . . , 125) and reconstruction of the data recordfrom the slides (121, 123, . . . , 125).

In one implementation, a centralized computer platform is provided toperform the storing (135) and retrieving (137) operations. The platformcontrols the private key (108) to the decryption (138) and records thecreation and uses of the data record in the blockchain ledger (102).However, the platform does not store persistently the data recordcontaining the token (104) and the encrypted data item (106). After eachsession of the storing (135) and retrieving (137) operations, the datarecord is purged from the platform.

In some implementations, the centralized computer platform is notresponsible for the decryption (138). A computer system that isauthorized to use the data item (105) controls the private key (108).For example, if the data item (105) is initially submitted to a socialnetworking site for the registration of a social networking account, thepublic key (107) of the social networking site is used for theencryption (131); and the private key (108) of the social networkingsite is required for the decryption (133).

Alternatively, or in combination, the storing (135) operation can beperformed by other computing devices. For example, when a web browser ofa user computer communicates with a social networking site to registeran account, the web browser may obtain the public key (107) of thecentralized computer platform (or the social networking site) togenerate the encrypted data item (106), obtain the token (104), store(135) the slices (121, 123, . . . , 125) in the trust database (101),and provide the token (104) to the social networking site.Alternatively, the web browser communicates the data item to thecentralized computer platform (or the social networking site), whichencrypts (131) the data item, and stores (135) the slices (121, 123, . .. , 125).

In some instances, permitted uses of the data item is stored to controlthe access to the data record containing the token (104) and theencrypted data item (106). For example, the permitted use may be storedin the blockchain ledger (102) or a database of a computing system inpossession of the private key (108) such that the decryption (133) isperformed only for permitted uses.

In one implementation, a computer platform is configured to facilitatethe retrieval (137) to the data record containing the token (104) andthe encrypted data item (106). The platform can be implemented using acomputer system separate from the computer systems (111, 113, . . . ,115) in the trust database (101), or as a collaboration function of thecomputer systems (111, 113, . . . , 115) in the trust database (101).

For example, in response to a request to retrieve (137) a data recordthat contains the token (104), the computer platform determines theportions of the token (104) in the slices (121, 123, . . . , 125),requests the respective computer systems (111, 113, . . . , 115) toretrieve the slices (121, 123, . . . , 125) that contain the respectiveportions of the token (104) and reassemble the slices (121, 123, . . . ,125) into the data record.

Similarly, a request to retrieve (137) a data record can be made usingthe encrypted data item (106) as the key. For example, a computer systemin possession of the data item (105) may use the public key (107) togenerate the encrypted data item (106) to request the trust database(101) to provide the token (104) stored with the encrypted data item inthe data record.

In some instances, the portion of the token (104) (or the encrypted dataitem (106)) in a slice (e.g., 121) stored in a computer system (e.g.,111) in the trust database (101) is not unique among slices stored fordifferent data records. Thus, a query made using a token slice (or aslice of the encrypted data item (106)) may generate query results fromdifferent data records. To identify a correct set of slices for thereconstruction of a data record, the trust database (101) may storefurther data that can be used to identify a match of a set of slicesthat belong to the same data record. For example, the slice (121) can bestored with a hash of the combination of the other slices (123, . . . ,125) such that a correct set of slices can be selected for thereconstruction of a requested data record. In some instances, a serialnumber of the data record is used to assemble the slices. Someimplementations, the token (104) is not sliced; and each slice (121,123, . . . , 125) includes a complete copy of the token (104), which canbe correlated across slices (121, 123, . . . , 125) to reconstruct theencrypted data item (106).

The blockchain ledger (102) can be implemented in a network of usercomputers, such as the user computers from which the data items (e.g.,105) containing PII are initially submitted, or user computers that areregistered to participate in the protection of PII via the trustdatabase (101). Alternatively, or in combination, the activity recordsof the tokens (e.g., 104) can be stored in a centralized database, in atleast some of the computer systems (111, 113, . . . , 115), or in thetrust database (101) in a way similar to the storing of the data recordcontaining the token (104) and the encrypted data item (106).

In some implementations, one or more permitted use cases of the dataitem (105) are specified in accordance with an ontology or standardizednomenclature. The permitted use cases can be encoded within or with thedata token (104). A request to access the data token (104) can includean intended use case specified in accordance with the same ontology orstandardized nomenclature. Thus, the approval of the intended use caseidentified for the request to access the data token (104) can beautomated via matching the intended use case against the one or morepermitted use cases. For example, when an intended use case meets therequirements of any of the permitted use cases, the intended use casecan be approved automatically via an automated approval system. In someinstances, the automated approval system determines whether an intendeduse case can be approved based on a determination whether the one ormore permitted use cases encoded within or with the data token (104)contain the intended use case.

FIG. 2 shows a method to store a data item according to one embodiment.For example, the method of FIG. 2 can be implemented in the system ofFIG. 1.

The method of FIG. 2 includes: creating (201) a token (104) thatuniquely identify a data item (105) among multiple data items; obtaining(203) a public key (107) of a public and private key pair; encrypting(205) the data item (105) using the public key (107) to generate ciphertext (106) of the data item (105); combining (207) the token (104) andthe cipher text (106) to generate a data record; dividing (209) the datarecord into a plurality of data slices (121, 123, . . . , 125); andstoring (211) the plurality of data slices (121, 123, . . . , 125) in arespective plurality of separate computer systems (111, 123, . . . ,125).

FIG. 3 shows a method to retrieve a data item according to oneembodiment. For example, the method of FIG. 3 can be implemented in thesystem of FIG. 1.

The method of FIG. 3 includes: storing (221) permission data identifyingpermitted uses of a data item (105) uniquely identified by a token (104)among multiple data items; retrieving (223), from a plurality ofseparate computers (111, 113, . . . , 115), a plurality of data slices(121, 123, . . . , 125) of a data record that contains the token (104);extracting (225) from the data record cipher text (106) of the data item(105); decrypting (227) the cipher text (106) into the data item (105)using a private key (108) that corresponds to a public key (107) used toencrypt (131) the data item (105) into the cipher text (106); recording(229), in a blockchain ledger (102), a use of the token (104); andproviding (231) the data item (105) for the use in accordance with thepermission data.

In some instances, the retrieving (223) of the data record from the setof separate computers (111, 113, . . . , 115) is in accordance with thepermission data.

In some instances, the extracting (225) of the cipher text from the datarecord is in accordance with the permission data.

In some instances, the decrypting (227) of the cipher text into the dataitem (105) is in accordance with the permission data.

For example, the governance of the data usage can be implemented using asystem discussed in U.S. patent application Ser. No. 15/685,305, filedAug. 23, 2017 and entitled “Systems and Methods to Control Data Accessand Usage”, the entire disclosure of which is hereby incorporated hereinby reference.

FIG. 4 shows a method to obtain a history of uses of a data itemaccording to one embodiment. For example, the method of FIG. 4 can beimplemented in the system of FIG. 1.

The method of FIG. 4 includes: receiving (241) a data item (105);obtaining (243) a public key (107) previously used to encrypt (131) thedata item (105) for storage; encrypting (245) the data item (105) togenerate cipher text (106) of the data item (105); searching (247)(e.g., in a trust database (101)) for a data record that contains thecipher text (106); obtaining (249), from the data record, a token (104)that uniquely represents the data item (105) in multiple data items; andquerying (251) a blockchain ledger (102) using the token (104) to obtainrecorded uses of the data item (105).

For example, the data item (105) may be a piece of PII of the user. Theuser may want to see the usage history of the PII by various computersystems. Thus, the user may use a web browser to visit a portal or runan application to retrieve the activity records stored in the blockchainledger (102) for the PII. The portal or the application regenerates theencrypted data item (106) to query the trust database (101) for thetoken (104) that represents in the data item (105). With the token(104), the portal or the application extracts the activity records ofthe token (104) and presents the activity history to the user.

At least one embodiment disclosed herein includes a distributed trustsystem and method that protects the PII of a user. For example, John Doegoes to www.company.com to register for an account. He enters his name,address, phone number, and/or other PII. He subsequently is provided aservice from the company to which he has signed up. When John hitssubmit on the registration screen, any fields marked as PII (which mayinclude even his password) are sent to a system that stores onlytemporarily the PII in memory and encrypts the PII, if it is not alreadyencrypted at the web interface layer by the browser of John or the webserver of the system. For example, the email address john@doe.com ofJohn is now a cipher text in the form of a text string similar toABCDEF123456. The cipher text is not a hash and can be decrypted asrequired. All of the data fields containing PII can be processed in asimilar way; and the encrypted data can be sliced into portions forspreading their storage across tens or hundreds of partner nodes of atrust database. The process can be used for web interfaces, SaaSapplications (using APIs), databases, and anything else that stores PIItoday.

A de-identifier can be used to encrypt a data item. Encryption has to beat least as long as the original text. A long email address willtherefore take more nodes to ensure it is sliced appropriately. Forexample, john@doe.com has 12 characters and can become a cipher text inthe form of A1B2C3D4E5F6 which can be decrypted to recover the datajohn@doe.com.

In some implementations, a data item is padded up to at least apredetermined length to facilitate proper slicing such that each slicehas a length longer than a threshold.

In one implementation, a platform (e.g., Personal Information Governor)is configured to create a natural key for a piece of PII that is to beprotected. In alternative implementations, the natural key might changerapidly (e.g., quantum keys). These keys are then used in places of therespective pieces of PII in databases where the person has associatednon-PII data, thus anonymizing the data.

The platform (e.g., Personal Information Governor) slices the encryptedPII data into equal parts and distributes the parts to multiplethird-parties via the internet along with the key created. For example,key1, ABCD may be sent to a bank where that portion of the slice is thenstored, key1, EF12 may go to a government agency, and key1, 3456 may goto a telecommunications company, by way of example.

Optionally, some portions of data normally defined as PII may not berepresented by tokens so long as it no longer identifies a singleperson. For example, a postal code may normally be categorized as PIIwhen used with an address, but if the address if removed from a computersystem of a company or government agency, then the postal code may beretained in the computer system. In another example, the first initialof a last name could in theory be allowed as well for purposes ofsorting basic admin work often done with things like sorting customers,etc.

After the encrypted PII has been sliced and sent to multiple differententities, a company or government agency has no data in any databasethat can identify a person. The data that can identify someone has beendistributed to a network of other organizations, each with only a smallpart of the encrypted data, which cannot be decrypted without both thekeys as well as the entire string of the encrypted data. Such anarrangement effectively removes the ability for a rouge agent within anorganization to steal PII data as it can no longer be associated to aspecific person.

For example, Mary Jane, a digital marketing specialist needs to send anemail blast to a section of customers telling them about the latestpromotion. She has identified a list of customers she would like to sendto and has filtered to identify the keys or tokens of a list of theselected customers. She now enters a web interface on the platform(e.g., Personal Information Governor) and requests to use the emailaddresses of these users for the permitted use of emailing them apromotion. Her company identification, company name, permitted use, timestamp, list of keys, the opt-in collection mark, and other fields aresubmitted and an administrator of the platform approves the access.Thus, the keys or tokens are used to retrieve and decrypt the emailaddresses from the trust database. Usage rules can be set based on thebreadth and sensitivity of the data or use case and additional approversmay be required (such as the Chief Reputation Officer (CRO) the ChiefExecutive Officer (CEO), or the Chief Operating Officer (COO)).

The complete setup data for the use case of Mary is then sent along withthe keys/tokens to the partner organizations, which will then providethe platform (e.g., Personal Information Governor) with the encryptedelements. The platform temporally puts the pieces back together,decrypts the data, and provides it to Mary for her campaign.Alternatively, this may be done by manipulating the email platform toreceive the tokens from Mary and the email platform will request andsubsequently receive the email addresses to resolve. In one embodiment,the same process can be done for physical mail, data analysis, and themany other use cases required of PII within an organization.

When the partner organizations receive the requests for PII encryptionslices, they may write the request details into a blockchain orequivalent immutable record. These records will then make up a way toimmutably audit the use of an identity within an organization and ensurecompliance and ethics are being followed.

Optionally, customer facing interfaces is provided to allow customers tosee all uses of their identity and secondarily opt-out of a particularuse case. For example, if a person was submitted to the system for anemail campaign, but the option flag was off, that person can also seethat they did not get the promotion because their flag was off andsecondarily opt-in. In an alternative embodiment, the system could bemonetized by the consumer (e.g., I'll sell you use of my PII or providein exchange for loyalty points, etc.)

Optionally, when a customer returns to the website and types their emailaddress and password, the data traverses in real time through theencryption and data slicer, finds a match, and the corresponding key isused to handle the remainder of their session. Optionally, a key can beassociated to a cookie so it doesn't need to be looked up during everylogin.

In one example, when an organization wishes to relocate PII to the trustdatabase (101), the organization creates a public and private key pairusing public key cryptography. The public key is made available to thepublic to allow PII to be stored as slices of encrypted PII acrossmultiple computer system (111, 113, . . . , 115).

When the organization has an data item (105) including PII, such as asocial security number (SSN), the organization stores the data item(105) in the trust database (101) and uses a token in its privatedatabase as a substitute of the data item. For example, the organizationobtains or generates a token that corresponds one-to-one with the dataitem (105) that identifies an individual person. the data item (105) isencrypted using the public key (107) to generate the cipher text (106).The cipher text (106) and the token (104) are stored together in thetrust database (101) as slices (121, 123, . . . , 125) that aredistributed among the separate computer systems (111, 113, . . . , 115).

When the organization that previously stored a data item (105)containing PII into the trust database (101) now wants to retrieve thePII, the organization determines the token (104) that corresponds to thedata item (105) containing the PII of the individual person. The trustdatabase (101) is queried using the token (104) to obtain the ciphertext (106) of the data item (105). The organization uses its private key(108) to decrypt the cipher text (106) and obtain the data item (105)containing the PII.

An individual person wishes to view the ledger transactions thatcorrespond to themselves and that are created by the organization. Theindividual person obtains the public key (107) published by theorganization and encrypts the data item (105) containing the PII usingthe public key (107) to generate the cipher text (106). The trustdatabase (101) is queried using the cipher text (106) to obtain thetoken(s) (e.g., 104). The ledger (102) is queried using the token (104)to retrieve the transaction records of the token (104).

In one implementation of consumer auditing, anyone can obtain the publickey to encrypt his/her data item (105) to generate the cipher text (106)to query the trust database (101) for his/her token (104), which canthen be used to query the ledger (102). Preferably, if someone does nothave a particular data item (105) in plaintext (e.g., SSN), this personcannot generate a correct cipher text (106) and thus cannot get his/hertoken (104) and thus cannot query the ledger (102). However, if theplaintext space is small (e.g., the total number of all possiblevariations of plaintext is small), an attacker can do a “hash reversal”attack by computing a dictionary of cipher text for all possiblevariations of plaintext. Then, the attacker has all of the valid ciphertext values to look up all of the tokens (104) for querying the ledger(102). Preferably, an identity verification process is used to verifythat the query is from the consumer identified by the PII. For example,the consumer may be validated via information that is not likely to beknown to others, such as the current car payment amount, etc.

FIG. 5 shows a data processing system that can be used to implement someof the components of the system according to one embodiment. While FIG.5 illustrates various components of a computer system, it is notintended to limit the implementations to any particular architecture ormanner of interconnecting the components. One embodiment may use othersystems that have fewer or more components than those shown in FIG. 5.

For example, each of the computer systems (111, 113, . . . , 115)illustrated in FIG. 1 can be implemented using one or more dataprocessing systems illustrated in FIG. 5, with fewer or more componentsthan those shown in FIG. 5.

For example, the blockchain ledger (102) illustrated in FIG. 1 can beimplemented in a network of computers, each of which is implementedusing one or more processing systems illustrated in FIG. 5, with feweror more components than those shown in FIG. 5.

For example, a computer platform (e.g., Personal Information Governor),or a user computer, can be implemented using one or more data processingsystems illustrated in FIG. 5, with fewer or more components than thoseshown in FIG. 5.

In FIG. 5, the data processing system (170) includes an inter-connect(171) (e.g., bus and system core logic), which interconnects amicroprocessor(s) (173) and memory (176). The microprocessor (173) iscoupled to cache memory (179) in the example of FIG. 5.

In one embodiment, the inter-connect (171) interconnects themicroprocessor(s) (173) and the memory (176) together and alsointerconnects them to input/output (I/O) device(s) (175) via I/Ocontroller(s) (177). I/O devices (175) may include a display deviceand/or peripheral devices, such as mice, keyboards, modems, networkinterfaces, printers, scanners, video cameras and other devices known inthe art. In one embodiment, when the data processing system is a serversystem, some of the I/O devices (175), such as printers, scanners, mice,and/or keyboards, are optional.

In one embodiment, the inter-connect (171) includes one or more busesconnected to one another through various bridges, controllers and/oradapters. In one embodiment the I/O controllers (177) include a USB(Universal Serial Bus) adapter for controlling USB peripherals, and/oran IEEE-1394 bus adapter for controlling IEEE-1394 peripherals.

In one embodiment, the memory (176) includes one or more of: ROM (ReadOnly Memory), volatile RAM (Random Access Memory), and non-volatilememory, such as hard drive, flash memory, etc.

Volatile RAM is typically implemented as dynamic RAM (DRAM) whichrequires power continually in order to refresh or maintain the data inthe memory. Non-volatile memory is typically a magnetic hard drive, amagnetic optical drive, an optical drive (e.g., a DVD RAM), or othertype of memory system which maintains data even after power is removedfrom the system. The non-volatile memory may also be a random accessmemory.

The non-volatile memory can be a local device coupled directly to therest of the components in the data processing system. A non-volatilememory that is remote from the system, such as a network storage devicecoupled to the data processing system through a network interface suchas a modem or Ethernet interface, can also be used.

In this description, some functions and operations are described asbeing performed by or caused by software code to simplify description.However, such expressions are also used to specify that the functionsresult from execution of the code/instructions by a processor, such as amicroprocessor.

Alternatively, or in combination, the functions and operations asdescribed here can be implemented using special purpose circuitry, withor without software instructions, such as using Application-SpecificIntegrated Circuit (ASIC) or Field-Programmable Gate Array (FPGA).Embodiments can be implemented using hardwired circuitry withoutsoftware instructions, or in combination with software instructions.Thus, the techniques are limited neither to any specific combination ofhardware circuitry and software, nor to any particular source for theinstructions executed by the data processing system.

While one embodiment can be implemented in fully functioning computersand computer systems, various embodiments are capable of beingdistributed as a computing product in a variety of forms and are capableof being applied regardless of the particular type of machine orcomputer-readable media used to actually effect the distribution.

At least some aspects disclosed can be embodied, at least in part, insoftware. That is, the techniques may be carried out in a computersystem or other data processing system in response to its processor,such as a microprocessor, executing sequences of instructions containedin a memory, such as ROM, volatile RAM, non-volatile memory, cache or aremote storage device.

Routines executed to implement the embodiments may be implemented aspart of an operating system or a specific application, component,program, object, module or sequence of instructions referred to as“computer programs.” The computer programs typically include one or moreinstructions set at various times in various memory and storage devicesin a computer, and that, when read and executed by one or moreprocessors in a computer, cause the computer to perform operationsnecessary to execute elements involving the various aspects.

A machine readable medium can be used to store software and data whichwhen executed by a data processing system causes the system to performvarious methods. The executable software and data may be stored invarious places including for example ROM, volatile RAM, non-volatilememory and/or cache. Portions of this software and/or data may be storedin any one of these storage devices. Further, the data and instructionscan be obtained from centralized servers or peer to peer networks.Different portions of the data and instructions can be obtained fromdifferent centralized servers and/or peer to peer networks at differenttimes and in different communication sessions or in a same communicationsession. The data and instructions can be obtained in entirety prior tothe execution of the applications. Alternatively, portions of the dataand instructions can be obtained dynamically, just in time, when neededfor execution. Thus, it is not required that the data and instructionsbe on a machine readable medium in entirety at a particular instance oftime.

Examples of computer-readable media include but are not limited torecordable and non-recordable type media such as volatile andnon-volatile memory devices, read only memory (ROM), random accessmemory (RAM), flash memory devices, floppy and other removable disks,magnetic disk storage media, optical storage media (e.g., Compact DiskRead-Only Memory (CD ROMS), Digital Versatile Disks (DVDs), etc.), amongothers. The computer-readable media may store the instructions.

The instructions may also be embodied in digital and analogcommunication links for electrical, optical, acoustical or other formsof propagated signals, such as carrier waves, infrared signals, digitalsignals, etc. However, propagated signals, such as carrier waves,infrared signals, digital signals, etc. are not tangible machinereadable medium and are not configured to store instructions.

In general, a machine readable medium includes any mechanism thatprovides (i.e., stores and/or transmits) information in a formaccessible by a machine (e.g., a computer, network device, personaldigital assistant, manufacturing tool, any device with a set of one ormore processors, etc.).

In various embodiments, hardwired circuitry may be used in combinationwith software instructions to implement the techniques. Thus, thetechniques are neither limited to any specific combination of hardwarecircuitry and software nor to any particular source for the instructionsexecuted by the data processing system.

The description and drawings are illustrative and are not to beconstrued as limiting. The present disclosure is illustrative ofinventive features to enable a person skilled in the art to make and usethe techniques. Various features, as described herein, should be used incompliance with all current and future rules, laws and regulationsrelated to privacy, security, permission, consent, authorization, andothers. Numerous specific details are described to provide a thoroughunderstanding. However, in certain instances, well known or conventionaldetails are not described in order to avoid obscuring the description.References to one or an embodiment in the present disclosure are notnecessarily references to the same embodiment; and, such references meanat least one.

The use of headings herein is merely provided for ease of reference, andshall not be interpreted in any way to limit this disclosure or thefollowing claims.

Reference to “one embodiment” or “an embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment is included in at least one embodiment of the disclosure. Theappearances of the phrase “in one embodiment” in various places in thespecification are not necessarily all referring to the same embodiment,and are not necessarily all referring to separate or alternativeembodiments mutually exclusive of other embodiments. Moreover, variousfeatures are described which may be exhibited by one embodiment and notby others. Similarly, various requirements are described which may berequirements for one embodiment but not other embodiments. Unlessexcluded by explicit description and/or apparent incompatibility, anycombination of various features described in this description is alsoincluded here. For example, the features described above in connectionwith “in one embodiment” or “in some embodiments” can be all optionallyincluded in one implementation, except where the dependency of certainfeatures on other features, as apparent from the description, may limitthe options of excluding selected features from the implementation, andincompatibility of certain features with other features, as apparentfrom the description, may limit the options of including selectedfeatures together in the implementation.

The disclosures of the above discussed patent documents are herebyincorporated herein by reference.

In the foregoing specification, the disclosure has been described withreference to specific exemplary embodiments thereof. It will be evidentthat various modifications may be made thereto without departing fromthe broader spirit and scope as set forth in the following claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative sense rather than a restrictive sense.

What is claimed is:
 1. A method to secure data from unauthorized access,the method comprising: receiving a public key of a computer systemauthorized to use a data item; providing a token representing the dataitem to the computer system as a substitute of the data item; encryptingthe data item using the public key into a cipher text that is to bedecrypted using a private key of the computer system; dividing thecipher text into multiple portions; and communicating the multipleportions to respective multiple computer systems that are separatelyadministrated by different organizations, wherein each respective systemof the multiple computer systems stores, in connection with the token,no more than a portion of the cipher text, which portion is notdecryptable using the private key without a remaining portion of thecipher text that is not stored in the respective system.
 2. The methodof claim 1, wherein the computer system authorized to use the data itemdoes not store persistently the data item.
 3. The method of claim 2,wherein in response to a request to use the data item, the computersystem retrieves the cipher text from the multiple computer systemsusing the token and decrypts the cipher text into the data item.
 4. Themethod of claim 3, further comprising: receiving the token; andcommunicating with the multiple computer systems to retrieve the ciphertext.
 5. The method of claim 4, further comprising: storing permissiondata identifying permitted uses of the data item represented by thetoken, the token is received in connection with a proposed use of thedata item; determining whether the proposed use is permitted accordingto the permission data; wherein the cipher text is retrieved in responseto a determination that the proposed use is permitted according to thepermission data.
 6. The method of claim 5, further comprising: storing,in a blockchain ledger and in response retrieval of the cipher text fromthe multiple computer systems, a record for the token, the recordcontaining information identifying an instance of use of the data item.7. The method of claim 6, further comprising: receiving the data itemfrom a user; regenerating the cipher text from the data item using thepublic key; and querying the multiple computer systems to retrieve thetoken associated with the cipher text.
 8. The method of claim 7, whereinthe each respective system of the multiple computer systems furtherstores data for correlating the portion of the cipher text, stored inthe respective system, with the remaining portion of the cipher textthat is not stored in the respective system.
 9. The method of claim 8,further comprising: retrieving, from the blockchain ledger, records forthe token; and presenting a use history of the data item according tothe records.
 10. The method of claim 5, wherein the data item includespersonally identifiable information.
 11. The method of claim 5, whereinone or more permitted use cases specified via an ontology orstandardized nomenclature are encoded within or with the data token torepresent one or more uses; wherein a request for access to the datatoken includes an intended use case specified via the ontology orstandardized nomenclature to represent a plurality of intended uses; andwherein approval of the intended use case to access the data token isautomated via matching the intended use case with the one or morepermitted use cases.
 12. The method of claim 11, further comprising:determining, by an automated system, whether the intended use case iscontained within the one or more permitted use cases for the data token.13. An apparatus, comprising: at least one microprocessor; and memorystoring instructions to instruct the at least one microprocessor tocommunicate with: a user computer providing a data item containingpersonally identifiable information; a computer system of anorganization as a recipient of the data item; and multiple computersystems that are separately administrated by different organizations;wherein in response to the user computer providing the data item, theinstructions are configured to instruct the at least one microprocessorto: receive a public key of the computer system as the recipient of thedata item, wherein a token representing the data item is provided to thecomputer system as a substitute of the data item; encrypt the data itemusing the public key into a cipher text that is to be decrypted using aprivate key of the computer system; divide the cipher text into multipleportions; and store, into the multiple computer systems in connectionwith the token, the multiple portions of the cipher text, wherein eachrespective system of the multiple computer systems stores no more than aportion of the cipher text, which portion is not decryptable using theprivate key without a remaining portion of the cipher text that is notstored in the respective system.
 14. The apparatus of claim 13, whereinthe computer system as the recipient of the data item does not storepersistently the data item.
 15. The apparatus of claim 14, wherein inresponse to a request to use the data item, the computer system as therecipient of the data item retrieves the cipher text from the multiplecomputer systems using the token and decrypts the cipher text into thedata item.
 16. The apparatus of claim 15, wherein in response toreceiving a request containing the token, the apparatus communicateswith the multiple computer systems to retrieve the cipher text.
 17. Theapparatus of claim 16, wherein the apparatus stores permission dataidentifying permitted uses of the data item represented by the token;the token is received in connection with a proposed use of the dataitem; and the cipher text is retrieved in response to a determinationthat the proposed use is permitted according to the permission data. 18.The apparatus of claim 17, wherein the apparatus further stores, in ablockchain ledger and in response retrieval of the cipher text from themultiple computer systems, a record for the token, the record containinginformation identifying an instance of use of the data item.
 19. Theapparatus of claim 18, wherein in response to a request containing thedata item from a user, the apparatus regenerates the cipher text fromthe data item using the public key, and queries the multiple computersystems to retrieve the token associated with the cipher text.
 20. Theapparatus of claim 19, wherein the each respective system of themultiple computer systems further stores data for correlating theportion of the cipher text, stored in the respective system, with theremaining portion of the cipher text that is not stored in therespective system.
 21. The apparatus of claim 19, wherein the apparatusretrieves, from the blockchain ledger, records for the token; andpresents a use history of the data item according to the records.
 22. Anon-transitory computer storage medium storing instructions which, whenexecuted on a computing apparatus, cause the computing apparatus toperform a method, the method comprising: in response to a user computerproviding data item containing personally identifiable information,obtaining a public key of a computer system of an organization as arecipient of the data item; identifying a token representing the dataitem; providing the token to the computer system as a substitute of thedata item; encrypting the data item using the public key into a ciphertext that is to be decrypted using a private key of the computer system;dividing the cipher text into multiple portions; and storing, intomultiple computer systems that are separately administrated by differentorganizations and in connection with the token, the multiple portions ofthe cipher text, wherein each respective system of the multiple computersystems stores no more than a portion of the cipher text, which portionis not decryptable using the private key without a remaining portion ofthe cipher text that is not stored in the respective system.